home *** CD-ROM | disk | FTP | other *** search
- Date: Sun, 6 Nov 94 04:30:06 PST
- From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
- Errors-To: TCP-Group-Errors@UCSD.Edu
- Reply-To: TCP-Group@UCSD.Edu
- Precedence: List
- Subject: TCP-Group Digest V94 #250
- To: tcp-group-digest
-
-
- TCP-Group Digest Sun, 6 Nov 94 Volume 94 : Issue 250
-
- Today's Topics:
- smtp gateway and dns
-
- Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
- Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
- Problems you can't solve otherwise to brian@ucsd.edu.
-
- Archives of past issues of the TCP-Group Digest are available
- (by FTP only) from UCSD.Edu in directory "mailarchives".
-
- We trust that readers are intelligent enough to realize that all text
- herein consists of personal comments and does not represent the official
- policies or positions of any party. Your mileage may vary. So there.
- ----------------------------------------------------------------------
-
- Date: Sat, 05 Nov 94 11:15:06 UTC
- From: kd5lu@kd5lu.ampr.org
- Subject: smtp gateway and dns
-
- Scenario: I route my mail to a smtp gateway that also happens to be my
- domain name server. I just want my outgoing mail to go to the mail gateway
- and let forward it on. However, when I send a note to another location,
- the domain name server (it is connected to the internet) gives me back the
- ip address and my smtp sender then makes connection (or tries) to the
- recipient directly, which causes some problems. Is there a way I can
- configure my station to NOT do this ? I know if I drop the name server
- it works the way I want it to, but I hate to do that. Thanks in
- advance. 73 de Bill, kd5lu.
- ----------------------------------------------------------------------------
- kd5lu.ampr.org 44.28.0.119 (145.670) 44.28.1.39 (441.475)
- Internet Mail abernat@metronet.com
- Work Phone (214) 622-5445
- Home Phone (214) 242-1241
- ----------------------------------------------------------------------------
-
- ------------------------------
-
- End of TCP-Group Digest V94 #250
- ******************************
-